Subject: ATM-08 Available

From: "J. G. Dudley (444/4358)" <[email-masked]>
Date: Mon, 21 Oct 96 17:13:19 EDT

The latest version of the HPR/ATM document is available on the AIW
Document Repository.

Site:      networking.raleigh.ibm.com
Directory: /aiw/appn/hpr/
Files:     atm-08.psbin, atm-08.zipbin, atm-08.exebin

An example URL is:

ftp://networking.raleigh.ibm.com/pub/standards/aiw/appn/hpr/atm-08.psbin

The ATM Forum supplied an expert reviewer for the document.  Many thanks
to Chin Chiang of BELLCORE.  Most of his comments asked for alignment of
terminology and minor clarifications.  You will find minor changes is
sections 1.6.3, 2.6, 2.7.1.1, 2.7.1.1.1, 2.7.3, 2.8, 2.11, and 2.14.

As always, the changes in this version are marked with change bars.  The
following changes are included:

1. X.25-to-ATM service interworking was clarified in section 1.2.5 to
   better explain the responsibilities of the service interworking
   unit when supporting HPR traffic.
2. The signaling information for an ATM connection network TG does
   not need to include the native E.164 address of the gateway switch
   if the address of the ATM endsystem is in the private ATM endsystem
   E.164 format.  The gateway address is not required because the
   private E.164 ATM endsystem address can be converted into a native
   E.164 address.  See sections 1.6.3, 2.11, and D.2.2.1.5.
3. Description of the ILMI address registry function was clarified
   to indicate that there is no local part of a native E.164 address.
   In addition, address registry is an optional function at public UNIs,
   and some public networks may not provide the function; in that case,
   the entire ATM address must be system defined.  See sections 1.6.3
   and 2.11.
4. New section 2.4.3.1 was added based on input from Jim Cobban (Nortel).
   The section discusses implementation considerations when both
   LDLC and LLC2 are implemented.  The principal recommendation is
   to delay link station control block allocation until the LLC to
   be used for the link station is determined via the activation
   XID exchange.
5. Section 2.4.11 was clarified to indicate that the TEST command may
   at the sender's option contain a TEST data field.
6. One of the factors used to decide when a predefined TG numbers is
   required for a regular defined link is whether the ATM addresses of
   the nodes at the ends of the TG are carried in SETUP.  Section
   2.7.1.1 was clarified to explain that it is the carrying of a node's
   address when it is the calling party that is important.
7. Footnote 5 in section 2.7.1.1 was updated to indicate the
   specific parameters in a received SETUP that should not be checked.
8. Descriptions have been added for the reverse-graphic condition boxes
   in section 2.7.1.1.1.
9. As indicated in version 19, the calling party must include subfield
   X'4680' in prenegotiation XIDs for native defined ATM links in order
   to indicate the TG number.  In this situation, the XID exchange fails
   if no subfield X'4680' is received; sense data is defined in
   section 2.11.3 for this case.

Regards,
Gary Dudley